Summary

• align workspace template wording with current scheduler and memory behavior
• clarify that HEARTBEAT.md is a scheduler snapshot, not a hand-edited source of truth
• add light structure guidance for canon template files so future entries stay compact and consistent

Why

The default non-worker workspace templates had a few misleading or underspecified spots:

• HEARTBEAT.md implied manual edits were the primary way to manage schedules, while runtime actually syncs it from scheduler state
• some bootstrap guidance was a bit too rigid or ambiguous in tone
• the canon files started almost empty, which made it easy to accumulate inconsistent freeform notes

Validation

• uv run pytest tests/test_configure_workspace_bootstrap.py
• uv run pytest tests/test_memory_system.py